DO NOT MERGE NUP-2386 Experiment with renaming of RecordSensor region module #3632
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
May 16, 2017 13:17
…te the builtin regions registration to demonstrate failure witnessed by Matt
…nit__.py to match the renamed module to demonstrate that the class name of the python region may differ from its module name, as long as it's registered using the correct module name.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR demonstrates the issue "Problem moving module RecordSensor" described by @rhyolight in https://discourse.numenta.org/t/problem-moving-module-recordsensor/2309 and subsequently demonstrates the simple fix.
RecordSensorregion's module in thepyRegionsglobal variable insidesrc/nupic/engine/__init__.pyto fix the issue that was reproduced in the above step.